This chapter describes the Redundant NIC feature.
Redundant NIC is currently supported on the following adapters:
The following operating environments are supported:
Quick Failover, an extension to Redundant NIC, is available for the following adapter and microcode combinations on Windows NT 4.0 SP5, NetWare 4.11 and 4.2 with IWSP6A and NetWare 5.0 with NW5SP2A.
| Adapter | Microcode |
| IBM High-Speed 100/16/4 Token-Ring PCI Management Adapter | any |
| IBM 16/4 Token-Ring PCI Management Adapter | any |
| IBM 16/4 Token-Ring PCI Adapter 2 | PX15C0CT or later |
| IBM 16/4 Token-Ring PCI Adapter 2 with Wake on LAN | AL15DAAA or later |
| IBM High-Speed 100/16/4 Token-Ring PCI Adapter | HSS2DAB4 or later |
| IBM PCI Wake on LAN Token-Ring Adapter | PX14D0CS or later |
For more information about Quick Failover, see Quick Failover.
The Redundant NIC function provides a high-availability solution for your Windows NT Server 3.51 and 4.0 or NetWare 4.11, 4.2 and 5.0 server. This function maintains network connectivity in the event of an adapter- or lobe-related failure. You can assign a backup adapter to take control of the network connection if the active adapter fails.
The Redundant NIC function will initiate a failover when a cable fault or a hard error occurs on the adapter. A failover causes the driver to switch traffic from the active adapter to the backup adapter. The active and backup roles are traded between the adapters of the redundant pair.
In many cases, the failover to the backup adapter will occur seamlessly. Due to the failover latency involved in opening the backup adapter onto the ring, some protocols might require that sessions be reestablished. In either case, network connectivity is maintained and server downtime is avoided.
The Redundant NIC function provides a high-availability solution for your token-ring connected servers. The goal of Redundant NIC is to maintain network connectivity in the event of an adapter- or lobe-related failure.
During driver configuration, users can define a Redundant NIC pair. The pair consists of an active adapter and a backup adapter. The backup adapter will take over in the event of a failure on the active adapter. These failovers can occur continually as long as the backup adapter is operational. Redundant NIC is offered on Windows NT and NetWare server systems. The LAN Adapter Management Agent can be used to complement the Redundant NIC function on Windows NT.
The Agent will send a DMI indication and SNMP trap upon detecting the completion of a Redundant NIC failover. The Agent also allows a failover to be initiated via DMI or SNMP. The Agent also provides the addresses of the active and backup adapters, a running count of failovers and the status of the backup adapter. The Nways Management Applications format the contents of the failover SNMP trap into a clear message.
The combined Redundant NIC and Agent functions should be used on mission-critical servers, and the Nways Management Applications should be used to monitor those servers. Redundant NIC provides the continual network connectivity necessary for the clients using the Windows NT Server. The Agent sends the failover SNMP trap to the Nways Management Application, or any other SNMP-based network management application. Once notified of the server failover, the network administrator can correct the error. For example, the error might be an accidentally disconnected cable. Once the cable has been reconnected, the network administrator can then force a failover from the management application and restore the server's original adapter configuration.
Quick Failover (QFO) is an extension to original Redundant NIC. QFO reduces the failover time from around 30 seconds to less than 10 seconds, and it allows the primary and secondary adapter pair to be in any PCI slot in the system. QFO is supported on Windows NT 4.0 SP 5, NetWare (4.11, 4.2) with IWSP6A and NetWare 5.0 with NW5SP2A.QFO for NetWare also has an enhanced user interface from the original RNIC for NetWare release. You can find additional information on NetWare Quick Failover device driver parameters in the "Novell NetWare Server driver parameters" section of the User's Guide for your adapter.
In addition to having an adapter that supports this feature, you must also have the proper device driver and microcode. See Supported environments for a list of the device drivers and microcode. On Windows NT, if your adapter or microcode level is different from those listed, the device driver automatically defaults to the regular Redundant NIC functions.
Follow these instructions when setting up a Redundant NIC pair.
The LAN Adapter Management Agent Version 1.40 or later allows you to manage the Redundant NIC operation. In the event of a failover, the Agent sends an SNMP trap to notify that a failover has occurred. The user can also initiate a failover through the Agent. For more information about the Agent, see LAN Adapter Management Agent. For an example of using the Agent and Redundant NIC, see Example scenarios.
The Redundant NIC function is provided in two pieces: IBMRNIC.NLM and IBMTRPO.LAN. When a failover from the active to the backup adapter occurs, the only protocols that can be switched are IP and IPX. Any other protocol information that is bound to the active adapter will be lost.
| Note: | The only protocol information that is retained when a failover occurs is what is bound to the active adapter when the problem occurs. No conflicting protocols should be bound to the backup adapter. The only exception to this is when ROUTE.NLM is used. In that case, ROUTE.NLM should be bound to the active and backup adapters. |
Failovers can occur from the active to the backup adapter, and also from the backup to the active until a good connection is made. If the backup adapter is not an IBM token-ring PCI adapter, only one automatic failover to the backup is supported. The Redundant NIC NLM can monitor four pairs at one time.
IBMRNIC.NLM Version 2.53 or later has some new features. Quick Failover, which allows failovers to occur much more quickly than normal failovers, is a significant new feature. To take advantage of Quick Failover you must have IBMTRPO.LAN Version 2.46 or later. Additionally, your adapter must be using a microcode version specified in Supported environments or later. Use the flash update tool available from your manufacturer if an adapter microcode update is necessary. Failback is an additional new feature. Failback causes failovers to occur automatically when the secondary adapter is active and when it can be determined that the primary adapter could be active instead. This feature requires you to use Quick Failover on the primary adapter. Failback is enabled by default, but can be disabled when a pair is created. In Versions 2.53 or later of IBMRNIC.NLM, a new user interface allows you to create pairs more easily. This user interface replaces many of the command line functions used in previous versions of the Redundant NIC NLM. The user interface provides functions that allow the user to get the current status of all pairs, cause manual failovers to occur, change the switching status, create, remove, save and load pairs
Versions of IBMTRPO.LAN prior to Version 2.14 will not work with the Redundant NIC capability. To use Quick Failover you need IBMTRPO.LAN Version 2.46 or later along with an adapter using a microcode version specified in Supported environments or later. Each adapter must be plugged into the same ring on the network for the failover to be completely transparent to the clients communicating with the server.
The driver communicates adapter failures or cable disconnects to the IBMRNIC. NLM via the NESL/NEB interface. If ODINEB.NLM loads after the LAN driver, these messages are never sent to the IBMRNIC NLM by the NESL/NEB subsystem. If the IBMRNIC.NLM does not failover after a cable disconnect or failure, verify that ODINEB.NLM is loading before the LAN driver. Make sure that you do not unload ODINEB.NLM while IBMRNIC.NLM is loaded. ODINEB.NLM lets you unload it at any time even if other NLMs depend on it to be loaded.
If you use INETCFG.NLM to configure your system, follow the steps in Installation using INETCFG.NLM instead of the following INSTALL.NLM section.
Support packs are available at http://support.novell.com.
See Setting up a Redundant NIC pair for more information on IBMRNIC command line parameters.
| Note: | If the secondary adapter is not an IBM token-ring PCI adapter, the -backup parameter must be used on the pair line. Also, because the secondary adapter probably will not support the standby keyword, the primary adapter must be loaded with the standby keyword. |
| Note: | Double-check your AUTOEXEC.NCF every time that you use the INSTALL.NLM program. It is possible that the INSTALL.NLM will move or remove ODINEB.NLM. Make sure that it loads before the network driver (IBMTRPO.LAN) and that IBMRNIC loads after the network driver. |
Since the User-specified Protocol that you created does not exist, no protocols will actually be bound to the secondary adapter. You might notice error messages that point this out when the server is starting up. These messages are for information only; no action is required.
See Setting up a Redundant NIC pair.
| Note: | If the secondary adapter is not an IBM token-ring PCI adapter, the -backup parameter must be used on the IBMRNIC pair line. The primary adapter must also be loaded with the standby keyword. |
| Note: | Double-check your AUTOEXEC.NCF every time you use the INETCFG.NLM program. It is possible that the INETCFG.NLM will move or remove ODINEB.NLM. Make sure that it loads before the network driver (IBMTRPO.LAN) and that IBMRNIC loads after the network driver. |
Follow these instructions to prepare IBMRNIC.NLM to monitor your adapter pair.
The Redundant NIC NLM requires that several options be specified in order to create a pair. You can specify the options to IBMRNIC.NLM when you load the nlm or on the command line after IBMRNIC.NLM is loaded. To automate the commands on reboot, add them to your AUTOEXEC.NCF.
To complete the setup, you need the following information:
| Note: | If the IBM token-ring PCI adapter driver (IBMTRPO.LAN) is loaded with the option to enable Quick Failover, the adapter will not become active until a Redundant NIC pair is made with that adapter. You will not be able to use that adapter until a pair is made. |
To set up a pair when you load the NLM, use the following format:
load ibmrnic pair <pairname> -p<slot#> -s<slot#> | -x<base address>
[-r<ip_address>] [-backup]
If IBMRNIC is already loaded you can set up a pair by using the IBMRNIC keyword on the system console. Its format is:
ibmrnic pair <pairname> -p<slot#> -s|x<slot#> -r<ip_address>
[-backup]
A description of each parameter follows:
As stated previously, the ibmrnic command can be used on the system console after IBMRNIC.NLM is loaded. This command can be used to create a pair and to get help on creating pairs. A user interface is started on a panel separate from the System Console that is used to modify your pairs. In versions of the Redundant NIC NLM prior to Version 2.50 all redundant NIC operations were performed on the command line. Now, only the pair and help commands are supported. The new user interface provides all of the other functions along with some extra functions. The user interface allows you to create, remove, save, and load pairs. You can also perform manual failovers and change the switching mode. The most recent status of all configured pairs is always shown on the screen.
ibmrnic help
Enter ibmrnic help to show the valid options for the ibmrnic command.
ibmrnic pair
This command is described in Setting up a Redundant NIC pair.
Create
Press the Insert key to display a form that helps you create a pair. Fill in all of the fields of the form and select create. The fields are the pair name, the primary slot, the secondary slot/port, the IP router and failback enable/disable.
Delete
Press the Delete key to remove a pair. A list box with all configured pair names appears. Select the name of the pair you would like to remove. If more than one pair exists, there is an entry that you can select to remove all pairs.
Failover
Press the F8 key to cause a failover to occur on a pair that you select. A list box with all configured pairs appears. When you select a pair from the list, a failover occurs from the active to the backup on that pair.
Mode
Press the F9 key to change the switching mode of an adapter. Select the pair name for which you want to change the mode. Then select the new mode for that pair.
Normally the Redundant NIC pair will automatically failover from the active to the backup if a cable fault or adapter failure is detected. Use this command to change the mode of the pair so that an automatic failover will not occur. To prevent automatic failovers from occurring, set the pair to manual mode. In manual mode, the ibmrnic switch command is the only way to failover from the active to the backup adapter. Disabled mode will not allow failovers. You can use disabled mode when performing maintenance on the backup adapter.
Save
Press the F4 key to save the configuration of all of the current pairs to a file. You must save the configuration to one of the files that is specified in the list box that appears.
Load
Press the F5 key to load the configuration from a previously saved file and then select the file you want to use to restore your configuration.
The configuration can also be restored from one of the saved files when IBMRNIC.NLM initially loads. To do this, specify the number of the file your configuration was saved to. For example, if the file name is IBMRNIC0.DAT, then to load IBMRNIC with the configuration stored in IBMRNIC0.DAT you would enter:
load ibmrnic 0
The files operated on by the Save and Load options are located in the sys:/system directory of the server.
The status of all pairs is shown in the main portal of the IBMRNIC window. If a pair is configured the following information will be displayed: the pair name and LAA (locally administered address), the slots that the primary and secondary adapters are using, the switching mode of the pair (manual, automatic, or disabled), the current state of the primary adapter, the current state of the secondary adapter, the number of failovers that have occurred, and the time the last failover occurred. Because all of this information can not be shown at one time, you must press the F1 key to toggle between the pair information and the adapter information.
| Note: | The terms primary and secondary do not refer to which adapter is currently active. The primary adapter is initially the active adapter and was configured by using the -p<<slot#> option on the command line. The secondary adapter is initially the backup adapter and was referred to by -s<<slot#> or -x<<hex port#> on the command line. |
There are several possible states that apply to an adapter. The possible states are:
The Redundant NIC NLM can be used in a server that supports PCI Hot-Plug, but some manual intervention is required to maintain its proper operation. If an adapter is removed that is part of an IBMRNIC pair, then failovers will no longer occur. If the active adapter in a pair is removed, then a failover will occur. After a hot-plug operation has been completed, the adapter driver must be loaded manually. Do not let HWDETECT.NLM attempt to automatically load the driver for the adapter. HWDETECT.NLM will not load the driver with the correct parameters needed to get the Redundant NIC pair operational again.
To perform a failover, perform the following procedure:
| Note: | If the secondary adapter is not an IBM token-ring PCI adapter ,and you are trying to reload its driver, you might have problems if the driver does not have an equivalent of the standby parameter. |
set Time Zone = EST5EDT
set Daylight Savings Time Offset = 1:00:00
set Start Of Daylight Savings Time = (APRIL SUNDAY FIRST 2:00:00 AM)
set End Of Daylight Savings Time = (OCTOBER SUNDAY LAST 2:00:00 AM)
set Default Time Server Type = SINGLE
# Note: The Time zone information mentioned above
# should always precede the SERVER name.
set Bindery Context = O=workgroup
file server name NWSRV1
ipx internal net 60990060
# The network environment for this server consists
# of a Token-Ring LAN with only one Frame Type
load tcpip
load odineb
# Primary adapter
LOAD IBMTRPO SLOT=3 RNICOPEN=400010203182 FRAME=TOKEN-RING NAME=IBMTRPO_1_TOK
BIND IPX IBMTRPO_1_TOK NET=ABCD1
# Secondary adapter loaded with the same frame type as the Primary
LOAD IBMTRPO SLOT=2 RNICOPEN=400010203182 FRAME=TOKEN-RING
NAME=IBMTRPO_2_TOK
# Create the Redundant NIC pair with Primary slot=3, and Secondary Slot=2
load ibmrnic pair mypair -p3 -s2
mount all
set Time Zone = EST5EDT
set Daylight Savings Time Offset = 1:00:00
set Start Of Daylight Savings Time = (APRIL SUNDAY FIRST 2:00:00 AM)
set End Of Daylight Savings Time = (OCTOBER SUNDAY LAST 2:00:00 AM)
set Default Time Server Type = SINGLE
# Note: The Time zone information mentioned above
# should always precede the SERVER name.
set Bindery Context = O=workgroup
file server name NWSRV1
ipx internal net 60990060
# The network environment for this server includes both Token-Ring frame
# types, utilizes Source Routing, has an IP network with a default IP gateway,
# and utilizes Route Switching via the IBM 8210
LOAD IPXRTR routing=NLSP
load tcpip
load odineb
# Primary Adapter
LOAD IBMTRPO SLOT=3 NODE=400010203182 RT=C FRAME=TOKEN-RING
NAME=IBMTRPO_1_TOK
BIND IPX IBMTRPO_1_TOK NET=ABCD1
LOAD IBMTRPO SLOT=3 NODE=400010203182 RT=C FRAME=TOKEN-RING_SNAP
NAME=IBMTRPO_1_TSP
BIND IPX IBMTRPO_1_TSP NET=FF1
BIND IP IBMTRPO_1_TSP ADDR=10.20.31.82 MASK=ff.ff.ff.0 GATE=10.20.31.254
# Secondary Adapter with the same frame types as Primary loaded, but no
# bindings
LOAD IBMTRPO SLOT=2 NODE=400010203182 STANDBY RT=C
FRAME=TOKEN-RING NAME=IBMTRPO_2_TOK
LOAD IBMTRPO SLOT=2 NODE=400010203182 STANDBY RT=C
FRAME=TOKEN-RING_SNAP NAME=IBMTRPO_2_TSP
# Create the Redundant NIC pair with the Primary slot=3, the Secondary
# slot=2, and the Default IP gateway=10.20.31.254
load ibmrnic pair mypair -p3 -s2 -r10.20.31.254
# If Source Routing is needed, then route.nlm must be loaded for
# all the logical boards of both the primary and secondary adapter
load route name=ibmtrpo_1_tok rsp=ar time=10
load route name=ibmtrpo_1_tsp rsp=ar time=10
load route name=ibmtrpo_2_tok rsp=ar time=10
load route name=ibmtrpo_2_tsp rsp=ar time=10
mount all
set Time Zone = EST5EDT set Daylight Savings Time Offset = 1:00:00 set Start Of Daylight Savings Time = (APRIL SUNDAY FIRST 2:00:00 AM) set End Of Daylight Savings Time = (OCTOBER SUNDAY LAST 2:00:00 AM) set Default Time Server Type = SINGLE # Note: The Time zone information mentioned above # should always precede the SERVER name. set Bindery Context = O=workgroup file server name NWSRV2 ipx internal net 35083DE8 ; Network driver LOADs and BINDs are initiated via ; INITSYS.NCF. The actual LOAD and BIND commands ; are contained in INITSYS.NCF and NETINFO.CFG. ; These files are in SYS:ETC. load odineb sys:etc\initsys.ncf load ibmrnic pair mypair -p7 -s6 mount all
# The network environment for this server consists
# of a Token-Ring LAN with only one Frame Type
LOAD SNMP
LOAD IBMTRPO NAME=TOK1_TOK FRAME=TOKEN-RING SLOT=7 NODE=400010203181
RXBUFFERS=32 TXBUFFERS=16 DATARATE=AUTO FULLDUPLEX=YES
RTSWENABLE=NO
LOAD IBMTRPO NAME=TOK2_TOK FRAME=TOKEN-RING SLOT=6 NODE=400010203181
RXBUFFERS=32 TXBUFFERS=16 DATARATE=AUTO FULLDUPLEX=YES STANDBY
RTSWENABLE=NO
BIND IPX TOK1_TOK net=abcd1 seq=1
LOAD DUMMY
BIND DUMMY TOK2_TOK
# The network environment for this server includes both Token-Ring frame
# types, utilizes Source Routing, has an IP network with a default IP gateway,
# and utilizes Route Switching via the IBM 8210
LOAD SNMP
LOAD IBMTRPO NAME=TOK1_TOK FRAME=TOKEN-RING SLOT=7 NODE=400010203181
RXBUFFERS=32 TXBUFFERS=16 DATARATE=AUTO FULLDUPLEX=YES
RT=C RTTS=1024
LOAD IBMTRPO NAME=TOK1_TSP FRAME=TOKEN-RING_SNAP SLOT=7 NODE=400010203181
RXBUFFERS=32 TXBUFFERS=16 DATARATE=AUTO FULLDUPLEX=YES
RT=C RTTS=1024
LOAD IBMTRPO NAME=TOK2_TOK FRAME=TOKEN-RING SLOT=6 NODE=400010203181
RXBUFFERS=32 TXBUFFERS=16 DATARATE=AUTO FULLDUPLEX=YES STANDBY
RT=C RTTS=1024
LOAD IBMTRPO NAME=TOK2_TSP FRAME=TOKEN-RING_SNAP SLOT=6 NODE=400010203181
RXBUFFERS=32 TXBUFFERS=16 DATARATE=AUTO FULLDUPLEX=YES
STANDBY RT=C RTTS=1024
LOAD IPXRTR ROUTING=NLSP
BIND IPX TOK1_TOK net=abcd1 seq=1
BIND IPX TOK1_TSP net=ff1 seq=2
LOAD ROUTE NAME=TOK1_TOK RSP=AR TIME=10
LOAD ROUTE NAME=TOK1_TSP RSP=AR TIME=10
LOAD ROUTE NAME=TOK2_TOK RSP=AR TIME=10
LOAD ROUTE NAME=TOK2_TSP RSP=AR TIME=10
LOAD Tcpip RIP=Yes Forward=No
BIND IP TOK1_TSP ARP=Yes Mask=ff.ff.ff.0 Address=10.20.31.81
LOAD DUMMY
BIND DUMMY TOK2_TOK
BIND DUMMY TOK2_TSP
set Time Zone = EST5EDT
set Daylight Savings Time Offset = 1:00:00
set Start Of Daylight Savings Time = (APRIL SUNDAY FIRST 2:00:00 AM)
set End Of Daylight Savings Time = (OCTOBER SUNDAY LAST 2:00:00 AM)
set Default Time Server Type = SINGLE
# Note: The Time zone information mentioned above
# should always precede the SERVER name.
set Bindery Context = O=workgroup
file server name NWSRV1
ipx internal net 60990060
# The network environment for this server consists
# of a Token-Ring LAN with only one Frame Type
load tcpip
load odineb
# Primary adapter 1
LOAD IBMTRPO SLOT=4 NODE=400000000004 DATARATE=M16 STANDBY FRAME=TOKEN-RING
NAME=IBMTRPO_4_TOK
BIND IPX IBMTRPO_4_TOK NET=1234
#Secondary adapter 1 (notice this adapter is not an IBM PCI Token-Ring
adapter)
LOAD IBMMPCO SLOT=5 NODE=400000000004 DATARATE=16 ENABLEFDX FRAME=TOKEN-RING
NAME=IBMMPCO_5_TOK
# Primary adapter 2
LOAD IBMTRPO SLOT=3 NODE=400010203182 FRAME=TOKEN-RING NAME=IBMTRPO_1_TOK
BIND IPX IBMTRPO_1_TOK NET=ABCD1
# Secondary adapter loaded with the same frame type as the Primary 2
LOAD IBMTRPO SLOT=2 NODE=400010203182 STANDBY FRAME=TOKEN-RING
NAME=IBMTRPO_2_TOK
# Create the Redundant NIC pair with Primary slot=4, and Secondary
# Slot=5 (this pair uses the -backup parameter because the Secondary
# adapter is not an IBM PCI Token-Ring adapter)
load ibmrnic pair bkpair -p4 -s5 -backup
# Create the Redundant NIC pair with Primary slot=3, and Secondary Slot=2
ibmrnic pair mypair -p3 -s2
mount all
| RNIC-100: | FAILED TO ALLOCATE MEMORY FOR LAN BOARDS
Explanation: Your server is not able to allocate memory for IBMRNIC.NLM User Action: Try unloading NLMs that are not needed or add more memory to the server. |
| RNIC-101: | FAILED TO REGISTER FOR ONE OR MORE NESL EVENTS.
Explanation: The Redundant NIC NLM was unable to register for some NESL/NEB events. This could prevent the Redundant NIC pairs from functioning correctly. User Action: Update MSM.NLM to the latest available level. |
| RNIC-102: | PAIRING SUCCEEDED
Explanation: A Redundant NIC pair was created successfully and will be monitored for events from the adapters that make up the pair. User Action: None. |
| RNIC-103: | MUST SPECIFY -P AND -S OR -X TO CREATE A REDUNDANT NIC PAIR
Explanation: The Redundant NIC NLM must be told the slot for the primary and secondary adapters when a pair is created. User Action: See Setting up a Redundant NIC pair for information about creating a pair. |
| RNIC-104: | MUST SPECIFY A NAME FOR A REDUNDANT NIC PAIR
Explanation: Redundant NIC pairs must be given a name for the pairing to be completed. User Action: Try to create the pair again and specify a pair name. |
| RNIC-105: | PAIR NAME IN USE. CHOOSE ANOTHER NAME.
Explanation: You tried to use an existing pair name for another pair. User Action: None. |
| RNIC-106: | THE DEFAULT IP ROUTER ADDRESS THAT WAS SPECIFIED IS INVALID.
Explanation: The default IP router address format that you specified was incorrect. User Action: Verify the IP address of your router. |
| RNIC-107: | UNABLE TO GET OPTIONS STRUCTURE MEMORY.
Explanation: There was a problem allocating memory. The server could be out of memory or there could be a problem with CLIB.NLM. User Action: Try unloading NLMs that are not needed or add more memory to the server. |
| RNIC-108: | NO REDUNDANT NIC PAIRS LOADED
Explanation: There are no configured pairs to show at this time. User Action: None. |
| RNIC-109: | ERROR READING PAIR INFORMATION FROM FILE
Explanation: Redundant NIC was unable to load one or more pairs from a saved configuration file. User Action: Try recreating the pairs and resaving the file. |
| RNIC-110: | ALL PAIRS WERE REMOVED.
Explanation: All Redundant NIC pairings were successfully removed. User Action: None. |
| RNIC-111: | INVALID REDUNDANT NIC PAIR NAME
Explanation: The pair name specified with the ibmrnic switch command does not exist. User Action: Use ibmrnic show to determine the correct name. |
| RNIC-112: | MANUAL ADAPTER FAILOVER SUCCEEDED
Explanation: An ibmrnic switch command was issued to a Redundant NIC pair and the failover completed successfully. User Action: None. |
| RNIC-113: | INVALID IBMRNIC SWITCH COMMAND
Explanation: The ibmrnic switch command that you specified was not correct. User Action: Enter ibmrnic help to get help with the ibmrnic command. |
| RNIC-114: | SWITCH MODE SET TO <MODE>
Explanation: The Redundant NIC switch mode was successfully set to the specified mode. User Action: None. |
| RNIC-115: | COULD NOT START THREAD TO HANDLE KEYBOARD REQUESTS
Explanation: A new thread failed to start. User Action: Unload the NLM and reload it. Some memory may need to be freed. |
| RNIC-116: | <PAIRNAME> UNPAIRED SUCCESSFULLY
Explanation: The Redundant NIC pair <pairname> was removed successfully. User Action: None. |
| RNIC-117: | UNKNOWN OR MALFORMED COMMAND
Explanation: You typed in a command that was not valid. User Action: Type ibmrnic help to get help with the ibmrnic command. |
| RNIC-118: | ERROR SAVING PAIR INFORMATION TO THE FILE
Explanation: The configuration for the pairs could not be saved. User Action: Verify that there is space available for new files. |
| RNIC-119: | THE SETTINGS WERE SAVED TO THE FILE SUCCESSFULLY
Explanation: The current configuration was correctly saved to a file. User Action: None. |
| RNIC-120: | USE THE IBMRNIC UTILITY SCREEN TO PERFORM THIS OPERATION
Explanation: Instead of using the console command line, use the NWSNUT interface. User Action: Try performing the command using the NWSNUT utility. |
| RNIC-121: | INVALID FILE NUMBER SPECIFIED
Explanation: The file number specified on the command line is invalid. User Action: Choose a file number from that is valid. |
| RNIC-122: | THE FAIL BACK FUNCTION COULD NOT BE STARTED
Explanation: The thread that performs the fail back function did not start. User Action: Unload and then reload IBMRNIC.NLM. |
| RNIC-123: | THE GRAPHICAL INTERFACE WAS NOT INITIALIZED
Explanation: There was a problem starting the NWSNUT utility for Redundant NIC. User Action: Try unloading and then reloading IBMRNIC.NLM. |
| RNIC-124: | CREATING DEFAULT INI FILE
Explanation: A default INI file is being created because the current INI file cannot be found. User Action: None. |
| RNIC-125: | INVALID FILE FORMAT, USING BUILT IN DEFAULTS
Explanation: The INI file is invalid and will not be used. User Action: Correct the problem introduced to the INI file or delete it so IBMRNIC can recreate the default file. |
| RNIC-126: | INVALID VALUE IN INI FILE
Explanation: An entry in the INI file was found to be incorrect. User Action: Correct any problems in the INI file. |
| RNIC-127: | COULD NOT START THREAD TO HANDLE COMMAND LINE
Explanation: The thread that processes the IBMRNIC command line did not get started. User Action: Try unloading and reloading IBMRNIC.NLM. |
| RNIC-128: | PROBLEM ALLOCATING RESOURCE TAGS
Explanation: There was not enough memory to allocate resource tags for IBMRNIC.NLM. User Action: Unload and reload IBMRNIC.NLM. |
| RNIC-200: | UNABLE TO GET PARAMETER STRUCTURE MEMORY
Explanation: Your server is not able to allocate memory for IBMRNIC.NLM. User Action: Try unloading NLMs that are not needed or add more memory to the server. |
| RNIC-201: | SETUP FAILED: INVALID COMMAND LINE FORMAT
Explanation: You typed an ibmrnic pair parameter that was not valid. User Action: Enter ibmrnic help to get help with the ibmrnic command. |
| RNIC-202: | SETUP FAILED: UNABLE TO GET MEMORY FOR RNIC PROFILE
Explanation: Your server is not able to allocate memory for IBMRNIC.NLM. User Action: Try unloading NLMs that are not needed or add more memory to the server. |
| RNIC-203: | SETUP FAILED: PROBLEM INITIALIZING THE ADAPTER PAIR
Explanation: The initialization routine for the pair failed. User Action: Try creating the pair again. |
| RNIC-204: | SETUP FAILED: PARAMETERS STRUCTURE IS MISSING
Explanation: There was a problem accessing the parameters structure. User Action: Try setting up the pair again. |
| RNIC-205: | SETUP FAILED: FAILED TO FIND ANY LOADED IBM TOKEN-RING
BOARDS.
Explanation: The Redundant NIC NLM was not able to find any IBM token-ring boards loaded at this time. User Action: Load token-ring boards for the primary and secondary adapters. |
| RNIC-206: | SETUP FAILED: PRIMARY ADAPTER NOT FOUND
Explanation: There is no adapter in the slot that you specified as primary. User Action: Specify the correct slot. |
| RNIC-207: | SETUP FAILED: COULD NOT ALLOCATE SPACE TO READ THE MSM CONFIG TABLE
Explanation: Problem allocating memory. It is possible that the machine is low on RAM. User Action: Try unloading NLMs that are not needed or add more memory to the server. |
| RNIC-208: | SETUP FAILED: PROBLEM READING THE MSM CONFIG TABLE
Explanation: The Config table for the adapter could not be read. User Action: Make sure that you are using the correct LAN driver. |
| RNIC-209: | SETUP FAILED: INCORRECT LAN DRIVER VERSION
Explanation: Your LAN driver is too old. User Action: Use the one that came with the IBMRNIC.NLM diskette or a newer version if one is available. |
| RNIC-210: | SETUP FAILED: SECONDARY ADAPTER NOT FOUND
Explanation: There is no adapter in the slot that you specified as secondary. User Action: Specify the correct slot. |
| RNIC-211: | SETUP FAILED: PRIMARY AND SECONDARY LOGICAL BOARDS DO NOT MATCH
Explanation: The logical boards on the primary adapter do not match the logical boards on the secondary adapter. User Action: Check the frame types for the primary and secondary adapters. They should match. |
| RNIC-212: | SETUP FAILED: PRIMARY AND SECONDARY MAC ADDRESSES DO NOT MATCH
Explanation: The same Locally Administered Address must be assigned to each adapter using the node address=<LAA> command line keyword. User Action: Set the Locally Administered Address on the primary and secondary adapters to the same address. |
| RNIC-213: | SETUP FAILED: COULD NOT FIND MLID CONFIG TABLE TO PERFORM ADAPTER
STATUS CHECK
Explanation: There is a problem reading the adapter Config table. User Action: Try setting up the pair again. |
| RNIC-214: | SETUP FAILED: THE PRIMARY ADAPTER MUST NOT BE SHUT DOWN
Explanation: The primary adapter must be open in order for Redundant NIC to initialize correctly. User Action: Specify a primary adapter that is not shut down. |
| RNIC-215: | SETUP FAILED: THE SECONDARY ADAPTER MUST NOT BE OPEN
Explanation: The secondary adapter must be closed when Redundant NIC is being initialized. User Action: Specify an adapter that was loaded with the standby keyword. |
| RNIC-216: | SETUP FAILED: THE PRIMARY ADAPTER COULD NOT ACCEPT THE LAA
Explanation: There was a problem setting up the adapter with the Quick Failover feature. User Action: Make sure the correct level of microcode is on the adapter. |
| RNIC-217: | SETUP FAILED: COULD NOT SHUT DOWN THE SECONDARY ADAPTER
Explanation: The secondary adapter did not respond to a request to shut down. User Action: Try setting up the pair again. |
| RNIC-218: | SETUP FAILED: THE PRIMARY ADAPTER SPECIFIED IS PART OF ANOTHER PAIR
Explanation: The primary adapter you specified is part of another Redundant NIC pair. User Action: Specify a primary adapter that is not part of a Redundant NIC pair. |
| RNIC-219: | SETUP FAILED: THE SECONDARY ADAPTER SPECIFIED IS PART OF ANOTHER
PAIR
Explanation: The secondary adapter you specified is part of another Redundant NIC pair. User Action: Specify a secondary adapter that is not part of a Redundant NIC pair. |
| RNIC-220: | SETUP FAILED: FAILED TO RESET THE PRIMARY ADAPTER
Explanation: The primary adapter could not be reset. User Action: Attempt to create the pair again. |
| RNIC-221: | SETUP FAILED: THE PRIMARY ADAPTER DOES NOT SUPPORT QUICK FAILOVER
Explanation: The primary adapter must have newer microcode to support Quick Failover. User Action: Update the microcode on the adapter or do not load the adapters driver with the RNICOPEN keyword. |
| RNIC-222: | SETUP FAILED: THE SECONDARY ADAPTER DOES NOT SUPPORT QUICK FAILOVER
Explanation: The secondary adapter must have newer microcode to support Quick Failover. User Action: Update the microcode on the adapter or do not load the adapters driver with the RNICOPEN keyword. |
| RNIC-223: | SETUP FAILED: THE PRIMARY AND SECONDARY ADAPTERS MUST NOT BE THE
SAME
Explanation: The primary and secondary adapters specified were the same adapter. User Action: Attempt to create the pair again with two adapters. |
| RNIC-300: | UNPAIR FAILED: INVALID IBMRNIC PAIR NAME
Explanation: The pair that you tried to remove does not exist. User Action: Enter ibmrnic show to find the correct pair name of the adapters that you would like to remove. |
| RNIC-301: | UNPAIR FAILED: COULD NOT REMOVE LINK FROM LIST OF PAIRS
Explanation: There was a problem unpairing the adapters. User Action: Try to remove the pair again. |
| RNIC-400: | MANUAL ADAPTER FAILOVER UNSUCCESSFUL: THE SWITCHING MODE IS
DISABLED.
Explanation: When the switching mode is disabled you cannot initiate a manual failover. User Action: Set the switching mode to manual or auto. |
| RNIC-401: | MANUAL ADAPTER FAILOVER UNSUCCESSFUL: THE BACKUP ADAPTER IS NOT
ABLE
TO BECOME ACTIVE AT THIS TIME.
Explanation: An attempt was made to failover to the backup adapter. The state of the backup adapter is preventing it from becoming an active adapter. User Action: Make sure that the backup adapter is not open. |
| RNIC-402: | MANUAL ADAPTER FAILOVER UNSUCCESSFUL: SHUTDOWN OF ACTIVE ADAPTER
FAILED
Explanation: The active adapter could not be shut down. User Action: Try issuing a manual failover from the command line. |
| RNIC-403: | MANUAL ADAPTER FAILOVER UNSUCCESSFUL: FAILED TO ACTIVATE BACKUP
ADAPTER.
Explanation: The backup adapter could not be reset. User Action: Try issuing a manual failover from the command line. |